Configuring a sandbox environment for malware testing

ABSTRACT

A device may receive a file to be analyzed in a sandbox environment, and may determine configuration information for configuring the sandbox environment. The configuration information may be determined based on at least one of: file information associated with the file to be analyzed, or client device information associated with a client device for which the file is intended. The device may configure the sandbox environment using the configuration information. The configuration information may identify a system configuration for the sandbox environment. The device may analyze the file in the sandbox environment based on configuring the sandbox environment using the configuration information.

BACKGROUND

Malicious software (“malware”) may refer to any software used to disruptcomputer operations, gather sensitive information, gain access toprivate computer systems, or the like. Malware may refer to a variety oftypes of hostile or intrusive software, including a computer virus, aworm, a trojan horse, ransomware, spyware, adware, scareware, or othermalicious software.

A sandbox environment may refer to a computing environment that may beused to test for malware. For example, a sandbox environment may be usedto execute untested code, untrusted software (e.g., from unverifiedthird parties), or the like. A sandbox environment may provide a tightlycontrolled set of resources for executing a software program withoutpermitting the software program to harm a device that hosts the sandboxenvironment. For example, the sandbox environment may restrict accessprovided to the software program (e.g., may restrict network access,access to inspect a host system, read and/or write access, etc.) toprevent harm to the host device.

SUMMARY

A device may receive a file to be analyzed in a sandbox environment, andmay determine configuration information for configuring the sandboxenvironment. The configuration information may be determined based on atleast one of: file information associated with the file to be analyzed,or client device information associated with a client device for whichthe file is intended. The device may configure the sandbox environmentusing the configuration information. The configuration information mayidentify a system configuration for the sandbox environment. The devicemay analyze the file in the sandbox environment based on configuring thesandbox environment using the configuration information.

A computer-readable medium may store one or more instructions that, whenexecuted by one or more processors, cause the one or more processors toreceive a file to be analyzed for malware using a sandbox environment.The one or more instructions may cause the one or more processors todetermine configuration information for configuring a systemconfiguration of the sandbox environment. The configuration informationmay be determined based on at least one of: file information associatedwith the file to be analyzed for malware, or client device informationassociated with a client device for which the file is intended. The oneor more instructions may cause the one or more processors to configurethe system configuration of the sandbox environment using theconfiguration information. The one or more instructions may cause theone or more processors to analyze the file for malware using the sandboxenvironment based on configuring the system configuration of the sandboxenvironment using the configuration information.

A method may include receiving, by a device, a file to be analyzed in acomputing environment. The method may include determining, by thedevice, configuration information for configuring the computingenvironment. The configuration information may be determined based on atleast one of: the file to be analyzed, or a client device for which thefile is intended. The method may include configuring, by the device, thecomputing environment using the configuration information. Theconfiguration information may identify a system configuration for thecomputing environment. The method may include analyzing, by the device,the file in the computing environment based on configuring the computingenvironment using the configuration information.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a diagram of an overview of an example implementationdescribed herein;

FIG. 2 is a diagram of an example environment in which systems and/ormethods, described herein, may be implemented;

FIG. 3 is a diagram of example components of one or more devices of FIG.2;

FIG. 4 is a flow chart of an example process for configuring a sandboxenvironment for malware testing; and

FIGS. 5A-5F are diagrams of an example implementation relating to theexample process shown in FIG. 4.

DETAILED DESCRIPTION

The following detailed description of example implementations refers tothe accompanying drawings. The same reference numbers in differentdrawings may identify the same or similar elements.

A security device (e.g., a firewall, a server, etc.) may use a sandboxenvironment to test a file for malware, such as by executing the file inthe sandbox environment and monitoring for an indication that the fileis malware. Different malware may be designed to exploit vulnerabilitiesof different system configurations (e.g., different operating systems,different types of devices, different applications, etc.). Furthermore,the security device may use the sandbox environment to protect differenttypes of client devices with different system configurations. Thus,using a standard sandbox environment (e.g., based on a default systemconfiguration, such as a corporate operating system image), regardlessof the file being tested for malware or the client device beingprotected from malware, may be less effective than configuring a customsandbox environment to test for malware. Implementations describedherein may assist in configuring a sandbox environment for malwaretesting based on a file being tested and/or a client device beingprotected, thereby increasing the effectiveness of malware testing andimproving computer security.

FIG. 1 is a diagram of an overview of an example implementation 100described herein. As shown in FIG. 1, a security device may receive afile for malware analysis. As further shown, the security device mayanalyze the file to determine file information for configuring a sandboxenvironment for a malware analysis. For example, the security device mayanalyze the file to determine an operating system type (e.g., anoperating system capable of executing the file, an operating systemvulnerable to the file, etc.), a source uniform resource identifier(URI) from which the file was obtained (e.g., which may indicate abrowser configuration, etc.), file metadata associated with the file, orthe like. The file information may indicate a system configuration to beused when configuring the sandbox environment. As shown, the securitydevice may configure the sandbox environment, for testing the file formalware, based on the file information. In this way, the sandboxenvironment may be configured and/or customized to more effectivelyanalyze the file for malware than if a default sandbox environment hadbeen used to analyze the file for malware.

In some implementations, the security device may identify a clientdevice for which the file is intended (e.g., a client device thatrequests the file, a client device to which the file is pushed, etc.).As further shown, the security device may determine client deviceinformation for configuring the sandbox environment for the malwareanalysis. For example, the security device may determine an operatingsystem executing on the client device, a default browser associated withthe client device, one or more applications installed on the clientdevice, or the like. The client device information may indicate a systemconfiguration to be used when configuring the sandbox environment, suchthat the sandbox environment may closely represent a systemconfiguration of the client device. As shown, the security device mayconfigure the sandbox environment, for testing the file for malware,based on the client device information. In this way, the sandboxenvironment may be configured and/or customized to more effectivelyanalyze a file for malware, when protecting a particular client device,than if a default sandbox environment had been used to analyze the filefor malware.

Implementations described herein may assist a security device withconfiguring and/or customizing a sandbox environment for testing a filefor malware. In some implementations, the security device may configurethe sandbox environment based on file information associated with thefile to be analyzed for malware. Additionally, or alternatively, thesecurity device may configure the sandbox environment based on clientdevice information associated with a client device for which the file isintended. The file information and the client device information aredescribed in more detail elsewhere herein. In some implementations, thesecurity device may use a probabilistic analysis (e.g., machinelearning) to configure the sandbox environment, as described in moredetail elsewhere herein. In this way, the security device may analyze afile for malware using a sandbox environment that is best suited for theanalysis.

FIG. 2 is a diagram of an example environment 200 in which systemsand/or methods, described herein, may be implemented. As shown in FIG.2, environment 200 may include one or more client devices 210-1 through210-N (N≧1) (hereinafter referred to collectively as “client devices210,” and individually as “client device 210”), a security device 220, acustomer network 230, and a network 240. Devices of environment 200 mayinterconnect via wired connections, wireless connections, or acombination of wired and wireless connections.

Client device 210 may include one or more devices associated with asystem configuration. For example, client device 210 may include adesktop computer, a laptop computer, a tablet computer, a mobile phone(e.g., a smart phone, a radiotelephone, etc.), a server, or a similartype of device. In some implementations, different client devices 210may have different system configurations, and may be impacted by malwarein different ways. In some implementations, client device 210 may becapable of executing a file that includes malware, which may cause harmto client device 210, information stored by client device 210, a user ofclient device 210, and/or another client device 210. In someimplementations, client device 210 may reside on customer network 230.In some implementations, client device 210 may configure and/or executea sandbox environment for malware testing on client device 210 (e.g.,instead of or in addition to security device 220 configuring and/orexecuting a sandbox environment for malware testing on security device220).

Security device 220 may include one or more devices capable ofprocessing and/or transferring network traffic associated with clientdevice 210, and/or capable of providing a security service (e.g., amalware detection service) for client device 210 and/or customer network230. For example, security device 220 may include a gateway, a firewall,a router, a bridge, a hub, a switch, a load balancer, an access point, areverse proxy, a server (e.g., a proxy server), or a similar type ofdevice. Security device 220 may be used in connection with a singleclient device 210 or a group of client devices 210 (e.g., client devices210 associated with a private network, a data center, etc.). In someimplementations, communications may be routed through security device220 to reach the group of client devices 210. For example, securitydevice 220 may be positioned within a network as a gateway to customernetwork 230 that includes the group of client devices 210. Additionally,or alternatively, communications from client devices 210 may be encodedsuch that the communications are routed to security device 220 beforebeing routed elsewhere.

In some implementations, security device 220 may configure and/orexecute a sandbox environment that may be used to analyze a file formalware. For example, security device 220 may configure and/or use thesandbox environment to monitor a file requested by and/or provided toclient device 210 (e.g., before the file is provided to client device210, after the file is provided to client device 210, etc.) to detectwhether the file includes malware. In some implementations, securitydevice 220 may determine configuration information, that identifies asystem configuration for configuring the sandbox environment, based onfile information (e.g., associated with a file to be tested formalware), client device information (e.g., associated with a clientdevice 210 for which the file is intended), or the like. Security device220 may configure the sandbox environment based on the configurationinformation, and may execute the file in the configured sandboxenvironment to detect whether the file includes malware.

Customer network 230 may include one or more wired and/or wirelessnetworks. For example, customer network 230 may include a local areanetwork (LAN), a private network, an intranet, a cloud computingnetwork, a cellular network (e.g., a long-term evolution (LTE) network,a 3G network, a code division multiple access (CDMA) network, etc.), apublic land mobile network (PLMN), a wide area network (WAN), ametropolitan area network (MAN), a telephone network (e.g., the PublicSwitched Telephone Network (PSTN)), an ad hoc network, the Internet, afiber optic-based network, or the like, and/or a combination of these orother types of networks. In some implementations, customer network 230may be a private network associated with client devices 210.

Network 240 may include one or more wired and/or wireless networks. Forexample, network 240 may include a cellular network, a PLMN, a LAN, aWAN, a MAN, a telephone network (e.g., the PSTN), a private network, anad hoc network, an intranet, the Internet, a fiber optic-based network,a cloud computing network, or the like, and/or a combination of these orother types of networks. In some implementations, security device 220may configure a sandbox environment for malware testing of a file,requested by client device 210 from a device (e.g., a server) associatedwith network 240, to determine whether the file includes malware.Additionally, or alternatively, a file may be pushed to client device210 (e.g., from a device associated with network 240), and securitydevice 220 may configure a sandbox environment for analyzing the file todetermine whether the file includes malware.

The number and arrangement of devices and networks shown in FIG. 2 areprovided as an example. In practice, there may be additional devicesand/or networks, fewer devices and/or networks, different devices and/ornetworks, or differently arranged devices and/or networks than thoseshown in FIG. 2. Furthermore, two or more devices shown in FIG. 2 may beimplemented within a single device, or a single device shown in FIG. 2may be implemented as multiple, distributed devices. For example, clientdevice 210 and security device 220 may be implemented as a singledevice, in some implementations. Additionally, or alternatively, a setof devices (e.g., one or more devices) of environment 200 may performone or more functions described as being performed by another set ofdevices of environment 200. For example, client device 210 may performone or more operations described herein as being performed by securitydevice 220.

FIG. 3 is a diagram of example components of a device 300. Device 300may correspond to client device 210 and/or security device 220. In someimplementations, client device 210 and/or security device 220 mayinclude one or more devices 300 and/or one or more components of device300. As shown in FIG. 3, device 300 may include a bus 310, a processor320, a memory 330, a storage component 340, an input component 350, anoutput component 360, and a communication interface 370.

Bus 310 may include a component that permits communication among thecomponents of device 300. Processor 320 is implemented in hardware,firmware, or a combination of hardware and software. Processor 320 mayinclude a processor (e.g., a central processing unit (CPU), a graphicsprocessing unit (GPU), an accelerated processing unit (APU), etc.), amicroprocessor, and/or any processing component (e.g., afield-programmable gate array (FPGA), an application-specific integratedcircuit (ASIC), etc.) that interprets and/or executes instructions.Memory 330 may include a random access memory (RAM), a read only memory(ROM), and/or another type of dynamic or static storage device (e.g., aflash memory, a magnetic memory, an optical memory, etc.) that storesinformation and/or instructions for use by processor 320.

Storage component 340 may store information and/or software related tothe operation and use of device 300. For example, storage component 340may include a hard disk (e.g., a magnetic disk, an optical disk, amagneto-optic disk, a solid state disk, etc.), a compact disc (CD), adigital versatile disc (DVD), a floppy disk, a cartridge, a magnetictape, and/or another type of computer-readable medium, along with acorresponding drive.

Input component 350 may include a component that permits device 300 toreceive information, such as via user input (e.g., a touch screendisplay, a keyboard, a keypad, a mouse, a button, a switch, amicrophone, etc.). Additionally, or alternatively, input component 350may include a sensor for sensing information (e.g., a global positioningsystem (GPS) component, an accelerometer, a gyroscope, an actuator,etc.). Output component 360 may include a component that provides outputinformation from device 300 (e.g., a display, a speaker, one or morelight-emitting diodes (LEDs), etc.).

Communication interface 370 may include a transceiver-like component(e.g., a transceiver, a separate receiver and transmitter, etc.) thatenables device 300 to communicate with other devices, such as via awired connection, a wireless connection, or a combination of wired andwireless connections. Communication interface 370 may permit device 300to receive information from another device and/or provide information toanother device. For example, communication interface 370 may include anEthernet interface, an optical interface, a coaxial interface, aninfrared interface, a radio frequency (RF) interface, a universal serialbus (USB) interface, a Wi-Fi interface, a cellular network interface, orthe like.

Device 300 may perform one or more processes described herein. Device300 may perform these processes in response to processor 320 executingsoftware instructions stored by a computer-readable medium, such asmemory 330 and/or storage component 340. A computer-readable medium isdefined herein as a non-transitory memory device. A memory deviceincludes memory space within a single physical storage device or memoryspace spread across multiple physical storage devices.

Software instructions may be read into memory 330 and/or storagecomponent 340 from another computer-readable medium or from anotherdevice via communication interface 370. When executed, softwareinstructions stored in memory 330 and/or storage component 340 may causeprocessor 320 to perform one or more processes described herein.Additionally, or alternatively, hardwired circuitry may be used in placeof or in combination with software instructions to perform one or moreprocesses described herein. Thus, implementations described herein arenot limited to any specific combination of hardware circuitry andsoftware.

The number and arrangement of components shown in FIG. 3 are provided asan example. In practice, device 300 may include additional components,fewer components, different components, or differently arrangedcomponents than those shown in FIG. 3. Additionally, or alternatively, aset of components (e.g., one or more components) of device 300 mayperform one or more functions described as being performed by anotherset of components of device 300.

FIG. 4 is a flow chart of an example process 400 for configuring asandbox environment for malware testing. In some implementations, one ormore process blocks of FIG. 4 may be performed by security device 220.In some implementations, one or more process blocks of FIG. 4 may beperformed by another device or a set of devices separate from orincluding security device 220, such as client device 210.

As shown in FIG. 4, process 400 may include receiving a file to beanalyzed in a sandbox environment (block 410). For example, securitydevice 220 may receive a file (e.g., an executable file, an application,a program, etc.) to be analyzed in a sandbox environment. In someimplementations, the file may be associated with client device 210(e.g., may be stored by client device 210, may be executing on clientdevice 210, may be requested by client device 210, may be sent to clientdevice 210, etc.). As an example, client device 210 may request a file(e.g., from a website, via an email link, etc.), and security device 220may receive and/or analyze the file before the file is provided toclient device 210. As another example, a file may be pushed to clientdevice 210, and security device 220 may receive the file (e.g., mayintercept the file before the file is received by client device 210, mayobtain the file after the file is received by client device 210, etc.).

In some implementations, security device 220 may analyze the file in asandbox environment. The sandbox environment may include a computingenvironment for testing the file for malware, and may be associated witha particular system configuration. For example, the sandbox environmentmay include a virtual computing environment executing on a virtualmachine with a particular system configuration. Security device 220 maycustomize the system configuration of the sandbox environment to providea more effective analysis of the file than if the sandbox environmentuses a standard or default system configuration, as described in moredetail elsewhere herein.

As further shown in FIG. 4, process 400 may include determining, basedon the file and/or a client device for which the file is intended,configuration information for configuring the sandbox environment (block420). For example, security device 220 may determine configurationinformation that identifies a system configuration for configuring thesandbox environment. In some implementations, security device 210 maydetermine the configuration information based on file information,client device information, or the like. In some implementations, fileinformation may include information determined based on the file to beanalyzed for malware (e.g., file information determined based onanalyzing the file). In some implementations, client device informationmay include information determined based on a client device 210 forwhich the file is intended (e.g., a client device 210 that requested thefile, a client device 210 toward which the file is pushed, a clientdevice 210 that receives the file, a client device 210 for which thefile is destined, etc.). Security device 220 may use the configurationinformation to configure the sandbox environment before testing the filefor malware.

The configuration information may identify a system configuration, suchas an operating system to be used by the sandbox environment (e.g., anoperating system type and/or version, such as Windows XP, Windows Vista,Windows 7, Windows 8, Android, iOS, OS X, etc.), a set of applicationsto be installed on and/or used by the sandbox environment (e.g., abrowser application, such as Internet Explorer, Chrome, Firefox, Safari,etc.; a document handler; a word processor; a spreadsheet application; aPortable Document Format (pdf) handler; a video player; a Flash player;a security application; a firewall; an anti-virus program; etc.), aversion of an application to be installed on and/or used by the sandboxenvironment (e.g., Internet Explorer version 7, 8, 9, 10, 11, etc.), aprocessor (e.g., CPU) architecture to be used by the sandbox environment(e.g., an ARM architecture, an x86 architecture, a 32-bit architecture,a 64-bit architecture, etc.), a compiler and/or an interpreter to beused by the sandbox environment (e.g., a Java virtual machine to be usedto compile and/or interpret Java code), a file structure to be used inthe sandbox environment, a network configuration to be used by thesandbox environment (e.g., a communication protocol used to communicatewith other devices, a port configuration for a set of ports, etc.), orthe like.

In some implementations, security device 220 may determine theconfiguration information based on file information associated with thefile. The file information may identify a system configuration, such asan operating system on which the file is capable of being executed, anapplication and/or a version of an application used to obtain the file(e.g., a browser and/or other application used to download the file), anapplication and/or a version of an application used to execute the file(e.g., a browser, a document handler, a word processor, a spreadsheetapplication, a pdf handler, a video player, a Flash player, etc.), aprocessor architecture capable of executing the file, a compiler capableof compiling the file, an interpreter capable of interpreting the file,a network configuration associated with the file (e.g., a communicationprotocol used by the file to communicate), or the like.

In some implementations, security device 220 may determine the fileinformation by analyzing the file for a file indicator that indicatesthe configuration information to be used for the file. The fileindicator may include, for example, a text string included in the file(e.g., a binary sample of the file), a source from which the file wasobtained (e.g., a uniform resource identifier (URI) used to obtain thefile, a website used to obtain the file, an application used to obtainthe file, an email used to obtain the file, etc.), file metadata (e.g.,static file information, such as a size of information included in thefile, an entropy or randomness of information included in the file,etc.), or the like.

Additionally, or alternatively, security device 220 may determine theconfiguration information based on client device information associatedwith a client device 210 for which the file is intended. The clientdevice information may identify a system configuration, such as anoperating system executing on client device 210 (e.g., an operatingsystem type and/or version), a set of applications and/or version(s) ofthe application(s) installed on and/or executing on client device 210(e.g., a browser and/or other application used to download the file), aset of default applications used to execute particular types of files onclient device 210 (e.g., a default browser, a default document handlerapplication, a default word processor, a default spreadsheetapplication, a default pdf handler application, a default video player,a default Flash player, etc.), a runtime library and/or a runtime systemused by client device 210, a processor architecture of client device210, a compiler used by client device 210, an interpreter used by clientdevice 210, a file structure associated with client device 210, anetwork configuration of client device 210, or the like.

In some implementations, security device 220 may determine the clientdevice information by analyzing client device 210 and/or receiving theclient device information from client device 210 and/or another device.As an example, security device 220 may request and/or receive the clientdevice information from client device 210 and/or another device thatstores client device information and/or analyzes client device 210 forthe client device information. In some implementations, security device220 may determine the client device information using an endpoint agent,a remote management agent, etc., used to manage client device 210.Additionally, or alternatively, security device 220 may determine theclient device information using a fingerprinting technique inassociation with client device 210 (e.g., operating systemfingerprinting). Additionally, or alternatively, security device 220 maydetermine the client device information by analyzing network trafficassociated with client device 210 (e.g., by analyzing historical networktraffic).

Additionally, or alternatively, security device 220 may load the clientdevice information from a data structure. For example, security device220 (or another device) may store a data structure that indicates arelationship between a particular client device 210 (e.g., using aclient device identifier, such as a network address, an Internetprotocol (IP) address, a media access control (MAC) address, a devicename, etc.) and client device information associated with the particularclient device 210 (e.g., a system configuration of client device 210).Security device 220 may identify the client device informationassociated with client device 210 using the client device identifier tosearch the data structure for the client device information.

In some implementations, security device 220 may determine theconfiguration information based on the file information (e.g., based onan operating system, a set of applications, etc., indicated by the fileinformation). In some implementations, security device 220 may determinethe configuration information based on the client device information(e.g., based on an operating system, a set of applications, etc.,indicated by the client device information). In some implementations,security device 220 may determine the configuration information based onboth the file information and the client device information.

In some implementations, the file information and the client deviceinformation may indicate conflicting (e.g., different) systemconfigurations for different types of configuration information (e.g.,may indicate different operating systems, different applications, etc.).In this case, security device 220 may select either the configurationinformation indicated by the file information or the configurationinformation indicated by the client device information to resolve theconflict (e.g., based on a user preference, based on a set of rules,etc.).

In some implementations, security device 220 may configure multiplesandbox environments with different system configurations, and mayanalyze the file in each of the multiple sandbox environments. Forexample, security device 220 may configure a first sandbox environmentbased on file information, may configure a second sandbox environmentbased on client device information, and may analyze the file using thefirst sandbox environment and the second sandbox environment.

In some implementations, security device 220 may perform a probabilisticanalysis of the file (e.g., based on file information) to determine theconfiguration information. For example, security device 220 maydetermine likelihoods that different system configurations (e.g.,configured using different configuration information) will identify thefile as malware. In this case, security device 220 may select, for thesandbox environment, the configuration information associated with thesystem configuration most likely to identify the file as malware (e.g.,as compared to other system configurations). Additionally, oralternatively, security device 220 may determine likelihoods thatdifferent system configurations will accurately identify whether thefile includes malware. In this case, security device 220 may select, forthe sandbox environment, the configuration information associated withthe system configuration most likely to accurately identify whether thefile is malware (e.g., as compared to other system configurations).

When security device 220 uses a probabilistic analysis to determine theconfiguration information, security device 220 may generate aprobabilistic model by training (e.g., using machine learning) differentsystem configurations using a training set of files (e.g., some of whichare known to be malware and some of which are known not to be malware).In this way, security device 220 may train the probabilistic model toindicate a likelihood that a particular system configuration willidentify a file as malware, a likelihood that a particular systemconfiguration will accurately identify whether a file is malware, or thelike, based on file information associated with the file. Securitydevice 220 may then use file information, associated with a file to betested, to determine one or more of these likelihoods when configuringthe sandbox environment.

In some implementations, security device 220 may determine a first typeof configuration information based on file information, may determine asecond type of configuration information based on client deviceinformation, and/or may determine a third type of configurationinformation based on a probabilistic analysis. Security device 220 maydetermine the types of configuration information to determine usingthese different techniques based on a user preference (e.g., receivedbased on user input), based on a set of rules, based on a set ofheuristics, or the like.

In some implementations, security device 220 may determine a first typeof configuration information based on the file information and/or theclient device information, but may not be able to determine a secondtype of configuration information based on the file information and/orthe client device information because the file information and/or theclient device information does not indicate the second type ofconfiguration information. In this case, security device 220 may use aprobabilistic analysis to determine the second type of configurationinformation.

As further shown in FIG. 4, process 400 may include configuring thesandbox environment based on the configuration information (block 430).For example, security device 220 may use the configuration informationto configure the sandbox environment. The configuration information mayidentify a system configuration for the sandbox environment, andsecurity device 220 may load and/or configure a sandbox environment withthe identified system configuration. In some implementations, securitydevice 220 may store sandbox profiles associated with different systemconfigurations for the sandbox environment, and may load a particularsandbox profile that matches (e.g., within a threshold degree ofsimilarity) the determined configuration information.

For example, security device 220 may configure and/or load a sandboxenvironment with a particular operating system, particular applicationsinstalled in the sandbox environment, particular default applicationsfor executing particular file types in the sandbox environment, or thelike. In some implementations, security device 220 may configure and/orload multiple sandbox environments with different system configurations.

As further shown in FIG. 4, process 400 may include analyzing the filein the sandbox environment based on configuring the sandbox environment(block 440), and determining whether the file includes malware (block450). For example, security device 220 may analyze the file for malwarein the sandbox environment. In some implementations, security device 220may analyze the file by executing the file in the sandbox environment,and by monitoring the file and/or the sandbox environment for behaviorindicative of malware. By analyzing the file in a customized sandboxenvironment rather than a standard sandbox environment, security device220 may increase the likelihood that the sandbox environment correctlyidentifies whether the file is malware, thereby improving informationsecurity.

As further shown in FIG. 4, if the file does not include malware (block450—NO), then process 400 may include permitting the file to be accessed(block 460). For example, if security device 220 does not determine thatthe file includes malware (e.g., after monitoring the file in thesandbox environment for a threshold amount of time), then securitydevice 220 may perform an action to permit the file to be accessed. Insome implementations, security device 220 may permit the file to beaccessed by identifying the file as unsuspicious. In this case, securitydevice 220 may store a malware indicator, in association with the file,that indicates that the file is unsuspicious (e.g., is not malware).

As another example, assume that client device 210 requests the file froma device associated with network 240 (e.g., a web server, a host server,etc.). In this case, security device 220 may receive the request, mayrequest the file from the device, may receive the file from the device,and may test the file in the configured sandbox environment beforesending the file to client device 210. Additionally, or alternatively,assume that a device, associated with network 240, pushes a file toclient device 210. In this case, security device 220 may receive thefile, and may analyze the file in the configured sandbox environmentbefore sending the file to client device 210. If security device 220determines that the file does not include malware, then security device220 may permit the file to be accessed by providing the file to clientdevice 210. In this way, security device 220 may protect client devices210, of customer network 230, from security threats.

As further shown in FIG. 4, if the file includes malware (block450—YES), then process 400 may include performing an action tocounteract the malware (block 470). For example, if security device 220determines that the file includes malware, then security device 220 mayperform an action to counteract the malware. In some implementations,security device 220 may counteract the malware by identifying the fileas suspicious. In this case, security device 220 may store a malwareindicator, in association with the file, that indicates that the file issuspicious (e.g., is malware). In this way, security device 220 and/oranother device may use the malware indicator to identify the file asmalware, and may perform an action to counteract the malware.

Additionally, or alternatively, security device 220 may counteract themalware by identifying the file (e.g., in memory) and deleting the filefrom memory. In this way, security device 220 may prevent the file fromharming security device 220 and/or client device 210.

As another example, assume that client device 210 requests the file froma device associated with network 240 (e.g., a web server, a host server,etc.). In this case, security device 220 may receive the request, mayrequest the file from the device, may receive the file from the device,and may test the file in the configured sandbox environment beforesending the file to client device 210. Additionally, or alternatively,assume that a device, associated with network 240, pushes a file toclient device 210. In this case, security device 220 may receive thefile, and may analyze the file in the configured sandbox environmentbefore sending the file to client device 210. If security device 220determines that the file includes malware, then security device 220 mayperform the action to counteract the malware by preventing the file frombeing provided to client device 210. In this way, security device 220may protect client devices 210, of customer network 230, from securitythreats.

In some implementations, if security device 220 determines that the fileincludes malware, then security device 220 may counteract the malware bymonitoring the file (e.g., by monitoring communications sent by thefile) to identify a device with which the file communicates (e.g., toidentify a command and control server). In this case, security device220 may block communications associated with the device, may provide aninstruction to client device 210 and/or another device associated withcustomer network 230 (e.g., a firewall, a router, a gateway, etc.) toblock communications associated with the device (e.g., to blockcommunications to and/or from the device), or the like. In this way,security device 220 may prevent a malicious file from harming clientdevice 210.

Additionally, or alternatively, security device 220 may provide anotification that identifies client devices 210 that are communicatingwith the device (e.g., the command and control server) to identify andprotect these client devices 210. In this way, security device 220 mayprotect client devices 210, of customer network 230, from securitythreats.

By configuring a sandbox environment based on configuration information(e.g., file information associated with a file to be tested for malware,client device information associated with client device 210 for whichthe file is intended, etc.), security device 220 may improve theeffectiveness of malware testing for files intended for client device210. For example, security device 220 may reduce false positive resultsand/or false negative results generated based on the testing, therebyproviding more accurate malware testing results and improvinginformation security of client device 210.

Although FIG. 4 shows example blocks of process 400, in someimplementations, process 400 may include additional blocks, fewerblocks, different blocks, or differently arranged blocks than thosedepicted in FIG. 4. Additionally, or alternatively, two or more of theblocks of process 400 may be performed in parallel.

FIGS. 5A-5F are diagrams of an example implementation 500 relating toexample process 400 shown in FIG. 4. FIGS. 5A-5F show an example ofconfiguring a sandbox environment for malware testing.

As shown in FIG. 5A, and by reference number 505, assume that a userinteracts with client device 210 to navigate to a website using abrowser, and to request a file, shown as “badfile.exe.” As shown byreference number 510, assume that the request is routed from clientdevice 210 to security device 220 before being routed to a web serverassociated with the website. As shown by reference number 515, assumethat security device 220 receives (e.g., intercepts) the file foranalysis before the file is provided to client device 210.

FIGS. 5B-5D show different options via which security device 220 maydetermine configuration information for configuring a sandboxenvironment for analyzing the file (e.g., badfile.exe). FIG. 5B shows anexample where security device 220 determines the configurationinformation based on file information. FIG. 5C shows an example wheresecurity device 220 determines the configuration information based onclient device information. FIG. 5D shows an example where securitydevice 220 determines the configuration information based on fileinformation and client device information.

As shown in FIG. 5B, and by reference number 520, in someimplementations, security device 220 may determine file informationassociated with the file to be analyzed (e.g., badfile.exe). Forexample, and as shown, security device 220 may analyze the file todetermine that the file is intended for execution in a Windows operatingsystem, and is intended for execution by Browser A. As shown byreference number 525, based on this file information, security device220 may load and/or configure a sandbox environment that includes aWindows operating system with Browser A installed and/or used as thedefault browser.

As shown in FIG. 5C, and by reference number 530, in someimplementations, security device 220 may determine client deviceinformation associated with client device 210 that requested the file.For example, and as shown, security device 220 may receive client deviceinformation that indicates that client device 210 is executing a Macoperating system, and has Application B installed. As shown by referencenumber 535, based on this client device information, security device 220may load and/or configure a sandbox environment that includes a Macoperating system with Application B installed and/or used as a defaultapplication for handling a particular type of file (e.g., an executablefile, such as badfile.exe).

As shown in FIG. 5D, and by reference number 540, in someimplementations, security device 220 may determine file information,associated with the file to be tested, and client device informationassociated with client device 210 that requested the file. For example,and as shown, security device 220 may receive file information thatindicates that the file is capable of being executed using a Windowsoperating system, and was requested using Browser C. As further shown,security device 220 may receive client device information that indicatesthat client device 210 is executing a Windows operating system, and usedBrowser C to request the file. Assume that security device 220 uses thisfile information and client device information to configure and/or loada sandbox environment that includes a Windows operating system andBrowser C.

As shown in FIG. 5E, and by reference number 545, assume that securitydevice 220 may select among multiple versions of a Windows operatingsystem for configuring the sandbox environment, shown as Windows VersionA, Windows Version B, and Windows Version C. As further shown, assumethat security device 220 has generated a probabilistic model, usingtraining data, and has applied file information for badfile.exe to theprobabilistic model to determine that Windows Version A has a 30%likelihood of identifying badfile.exe as malware, that Windows Version Bhas a 60% likelihood of identifying badfile.exe as malware, and thatWindows Version C has a 90% likelihood of identifying badfile.exe asmalware. As shown by reference number 550, assume that security device220 selects Windows Version C for configuring the sandbox environmentbecause Windows Version C has the highest likelihood of identifyingbadfile.exe as malware (e.g., as compared to Windows Version A andWindows Version B). For example, assume that security device 220 loadsand/or configures a sandbox environment that includes Windows Version C

As shown in FIG. 5F, and by reference number 555, assume that securitydevice 220 analyzes badfile.exe in the sandbox environment that includesWindows Version C, and determines that badfile.exe is malware. As shownby reference number 560, based on this determination, assume thatsecurity device 220 performs an action to counteract the malware. Forexample, and as shown by reference number 565, assume that securitydevice 220 prevents badfile.exe from being provided to client device210, which requested badfile.exe.

In this way, security device 220 may configure a custom sandboxenvironment to increase the effectiveness of malware detection based ona file being analyzed, based on a client device that requested the file,or the like. In this way, security device 220 may improve informationsecurity.

As indicated above, FIGS. 5A-5F are provided merely as an example. Otherexamples are possible and may differ from what was described with regardto FIGS. 5A-5F.

Implementations described herein may assist in configuring a sandboxenvironment for malware testing based on a file being tested and/or aclient device being protected, thereby increasing the effectiveness ofmalware testing and improving computer security.

The foregoing disclosure provides illustration and description, but isnot intended to be exhaustive or to limit the implementations to theprecise form disclosed. Modifications and variations are possible inlight of the above disclosure or may be acquired from practice of theimplementations.

As used herein, the term component is intended to be broadly construedas hardware, firmware, and/or a combination of hardware and software.

Some implementations are described herein in connection with thresholds.As used herein, satisfying a threshold may refer to a value beinggreater than the threshold, more than the threshold, higher than thethreshold, greater than or equal to the threshold, less than thethreshold, fewer than the threshold, lower than the threshold, less thanor equal to the threshold, equal to the threshold, etc.

It will be apparent that systems and/or methods, described herein, maybe implemented in different forms of hardware, firmware, or acombination of hardware and software. The actual specialized controlhardware or software code used to implement these systems and/or methodsis not limiting of the implementations. Thus, the operation and behaviorof the systems and/or methods were described herein without reference tospecific software code—it being understood that software and hardwarecan be designed to implement the systems and/or methods based on thedescription herein.

Even though particular combinations of features are recited in theclaims and/or disclosed in the specification, these combinations are notintended to limit the disclosure of possible implementations. In fact,many of these features may be combined in ways not specifically recitedin the claims and/or disclosed in the specification. Although eachdependent claim listed below may directly depend on only one claim, thedisclosure of possible implementations includes each dependent claim incombination with every other claim in the claim set.

No element, act, or instruction used herein should be construed ascritical or essential unless explicitly described as such. Also, as usedherein, the articles “a” and “an” are intended to include one or moreitems, and may be used interchangeably with “one or more.” Furthermore,as used herein, the terms “group” and “set” are intended to include oneor more items (e.g., related items, unrelated items, a combination ofrelated items and unrelated items, etc.), and may be usedinterchangeably with “one or more.” Where only one item is intended, theterm “one” or similar language is used. Also, as used herein, the terms“has,” “have,” “having,” or the like are intended to be open-endedterms. Further, the phrase “based on” is intended to mean “based, atleast in part, on” unless explicitly stated otherwise.

1. A device, comprising: one or more processors to: receive a file to beanalyzed in a sandbox environment; determine configuration informationfor configuring the sandbox environment, the configuration informationbeing determined based on at least one of: file information associatedwith the file to be analyzed, or client device information associatedwith a client device for which the file is intended, and theconfiguration information indicating a system configuration; determine afirst likelihood that the sandbox environment will identify the file asmalware based on the sandbox environment being configured using a firsttype of the system configuration, the first likelihood being determinedusing a probabilistic model, the probabilistic model being generatedusing a training set of files; determine a second likelihood that thesandbox environment will identify the file as malware based on thesandbox environment being configured using a second type of the systemconfiguration, the second likelihood being determined by using theprobabilistic model; configure the sandbox environment using the firsttype of the system configuration or the second type of the systemconfiguration; and analyze the file in the sandbox environment based onconfiguring the sandbox environment using the first type of the systemconfiguration or the second type of the system configuration.
 2. Thedevice of claim 1, where the one or more processors are further to:analyze the file to determine the file information; and where the one ormore processors, when determining the configuration information, are to:determine the configuration information, using the file information,based on analyzing the file to determine the file information.
 3. Thedevice of claim 1, where the file information identifies at least oneof: an operating system on which the file is capable of being executed,or an application capable of executing the file; where the one or moreprocessors, when determining the configuration information, are to:determine the configuration information based on the operating system orthe application; and where the one or more processors, when configuringthe sandbox environment, are to: configure the sandbox environment toinclude the operating system or the application.
 4. The device of claim1, where the one or more processors are further to: receive the clientdevice information; and where the one or more processors, whendetermining the configuration information, are to: determine theconfiguration information, using the client device information, based onreceiving the client device information.
 5. The device of claim 1, wherethe client device information identifies at least one of: an operatingsystem executing on the client device, or an application installed onthe client device; where the one or more processors, when determiningthe configuration information, are to: determine the configurationinformation based on the operating system or the application; and wherethe one or more processors, when configuring the sandbox environment,are to: configure the sandbox environment to include the operatingsystem or the application.
 6. The device of claim 1, where the one ormore processors, when determining the configuration information, are to:determine the configuration information based on the file informationand the client device information.
 7. The device of claim 1, where theone or more processors are further to: detect a conflict between firstconfiguration information identified based on the file information andsecond configuration information identified based on the client deviceinformation; and select the first configuration information or thesecond configuration information based on detecting the conflict; andwhere the one or more processors, when determining the configurationinformation, are further to: determine the configuration informationbased on selecting the first configuration information or the secondconfiguration information.
 8. A computer-readable medium storinginstructions, the instructions comprising: one or more instructionsthat, when executed by one or more processors, cause the one or moreprocessors to: receive a file to be analyzed for malware using a sandboxenvironment; determine configuration information for configuring asystem configuration of the sandbox environment, the configurationinformation being determined based on at least one of: file informationassociated with the file to be analyzed for malware, or client deviceinformation associated with a client device for which the file isintended, and the configuration information indicating the systemconfiguration; determine a first likelihood that the sandbox environmentwill identify the file as malware based on the sandbox environment beingconfigured using a first type of the system configuration, the firstlikelihood being determined using a probabilistic model, theprobabilistic model being generated using a training set of files;determine a second likelihood that the sandbox environment will identifythe file as malware based on the sandbox environment being configuredusing a second type of the system configuration, the second likelihoodbeing determined by using the probabilistic model; configure the systemconfiguration using the first type of the system configuration or thesecond type of the system configuration; and analyze the file formalware using the sandbox environment based on configuring the systemconfiguration using the first type of the system configuration or thesecond type of the system configuration.
 9. The computer-readable mediumof claim 8, where the one or more instructions, that cause the one ormore processors to determine the configuration information, cause theone or more processors to: determine the configuration information basedon the file information and not based on the client device information.10. The computer-readable medium of claim 8, where the one or moreinstructions, that cause the one or more processors to determine theconfiguration information, cause the one or more processors to:determine the configuration information based on the client deviceinformation and not based on the file information.
 11. Thecomputer-readable medium of claim 8, where the configuration informationidentifies at least one of: an operating system to be used for thesystem configuration; an application to be used for the systemconfiguration; or a processor architecture to be used for the systemconfiguration.
 12. The computer-readable medium of claim 8, where theone or more instructions, when executed by one or more processors,further cause the one or more processors to: identify the systemconfiguration from a plurality of system configurations; and load thesystem configuration in the sandbox environment.
 13. Thecomputer-readable medium of claim 8, where the one or more instructions,when executed by the one or more processors, further cause the one ormore processors to: select the system configuration, from a plurality ofsystem configurations that include the first type of the systemconfiguration and the second type of the system configuration, based on:the first likelihood, the second likelihood, or a user preference. 14.The computer-readable medium of claim 8, where the one or moreinstructions, when executed by the one or more processors, further causethe one or more processors to: select the system configuration, from aplurality of system configurations that include the first type of thesystem configuration and the second type of the system configuration,based on the first likelihood and the second likelihood, each of theplurality of system configurations being associated with a particularsandbox profile.
 15. A method, comprising: receiving, by a device, afile to be analyzed in a computing environment; determining, by thedevice, configuration information for configuring the computingenvironment, the configuration information being determined based on atleast one of: the file to be analyzed, or a client device for which thefile is intended, and the configuration information indicating a systemconfiguration; determining, by the device, a first likelihood that thecomputing environment will identify the file as malware based on thecomputing environment being configured using a first type of the systemconfiguration, the first likelihood being determined using aprobabilistic model, the probabilistic model being generated using atraining set of files; determining, by the device, a second likelihoodthat the computing environment will identify the file as malware basedon the computing environment being configured using a second type of thesystem configuration, the second likelihood being determined by usingthe probabilistic model; configuring, by the device, the computingenvironment using the first type of the system configuration or thesecond type of the system configuration, and analyzing, by the device,the file in the computing environment based on configuring the computingenvironment using the first type of the system configuration or thesecond type of the system configuration.
 16. The method of claim 15,further comprising: determining file information associated with thefile to be analyzed; and where determining the configuration informationcomprises: determining the configuration information based on the fileinformation.
 17. The method of claim 16, where the file informationidentifies at least one of: an operating system on which the file iscapable of being executed, a first application used to obtain the file,a second application used to execute the file, or a processorarchitecture capable of executing the file; and where determining theconfiguration information comprises: determining the configurationinformation based on at least one of: the operating system, the firstapplication, the second application, or the processor architecture. 18.The method of claim 15, further comprising: determining client deviceinformation associated with the client device for which the file isintended; and where determining the configuration information comprises:determining the configuration information based on the client deviceinformation.
 19. The method of claim 18, where the client deviceinformation identifies at least one of: an operating system executing onthe client device, a set of applications installed on the client device,a set of default applications used to execute particular types of fileson the client device, or a processor architecture of the client device;and where determining the configuration information comprises:determining the configuration information based on at least one of: theoperating system, the set of applications, the set of defaultapplications, or the processor architecture.
 20. The method of claim 15,further comprising: performing a probabilistic analysis based on atleast one of: file information associated with the file, or clientdevice information associated with the client device; and wheredetermining the configuration information comprises: determining theconfiguration information based on performing the probabilisticanalysis.